docs: map fork behavior for V2 convergence - #49

START

POLSYNC:BUILDER — START / CHECKPOINT (publishing the existing local pending receipt)

Kameron approved the bounded managed-policy sync on November 2, 2026. Scope: merge current pingdotgg/t3code main into branch builder/managed-policy-sync using a merge commit, preserve fork customizations, add a separate schema-only Closura policy change, run checks, and open the implementation PR(s). Do not merge PRs or deploy. This comment uses the existing V2 convergence planning PR as a coordination destination; it does not change or accept this planning PR's source.

Exact inputs: fork HEAD 7c146a2c344496f51a93f4cce90763b16cc62437; upstream/MERGE_HEAD 30654b3e91a51937d1dba18fc83af19d8003f5ca; merge-base d7819c18813fa03b033cc1c9472c9acc0ffc0618. Upstream includes pingdotgg#27197, merged November 1. There are 4,745 upstream commits and 65 fork commits relative to the common history.

The local merge initially had 141 conflicted paths. The first native Go resolution attempt was stopped before commit because bulk upstream selection did not establish semantic fork preservation. Its candidate is not accepted. A fresh read-only Go review found 12 repair groups: continuation/refusal integrity, governed Codex wiring/catalog/readiness, release provenance/workflow compatibility, owner-only reviewer tests, usage attribution/cache correctness, title preference, post-start receipts, launch preflight, Windows service and macOS profile wiring, CI mirror/runner consistency, and fixture output drain. Owner-only reviewer code, fork release helper defaults, relay owner admission, worktree defaults and attribution persistence were found retained; these must not be weakened to make tests pass.

Observed verification: vp i --no-frozen-lockfile passed with pinned Node 26.12.1 / pnpm 12.14.0. Initial scoped typechecks failed: contracts 2 errors, shared 8, server 428. This is an unaccepted working tree, not checks on a new commit. No PR head has been created or pushed. GitHub Actions is disabled for the fork; empty checks must not be called green. No repository settings were changed.

A single bounded native OpenCode Go repair worker owns this worktree; the parent T3 session retains foreground collection, verification and publication. Existing V2 adaptation commit 2f521e6d214512dc573df82c1d143405245439c9 was fetched read-only for selective reuse, not merged or accepted as a separate stack. No other source branch is being merged.

Policy feasibility: the upstream schema can set/lock a Codex model-selection default, restrict provider drivers, allow remote/Connect, set a full-access default, and direct desktop updates to a generic HTTPS feed. It cannot select a ChatGPT account/plan/workspace, directly name a GitHub release repository, pin CLI/npm updates, or force a minimum permission mode for every existing thread. The fork's latest release currently lacks generic-updater manifests. Exact limitations will appear in the policy README and implementation PR body; no fields or credentials will be invented.

Next owned action: finish faithful V2 source repair and focused tests, independently verify the exact candidate, then create/link the sync and policy PRs with required provenance. No PR merge, deployment, key rotation, purchase, other-human review request, or installed-policy change occurred. Overall task remains IN PROGRESS.

Model: codex/gpt-6.1-sol
Task: t3code managed-policy sync + Closura policy
Execution assistance: native OpenCode Go (DeepSeek initial partial candidate; MiMo preservation diagnosis and current repair), with honest attribution and no human approval claim.